How to install Chrome extensions on Firefox
You cannot install a Chrome extension from the Chrome Web Store directly in Firefox. The practical way to get Chrome extensions on Firefox is to install the same extension's Firefox version from addons.mozilla.org (AMO). Most popular extensions publish one. If none exists, the extension needs to be ported by its developer, because the old converter add-on, Chrome Store Foxified, no longer works.
This guide shows how to find the Firefox version, what the old converter did, and how developers test a Chrome extension in Firefox.
Can Firefox run Chrome extensions?
Firefox can run extensions built with the WebExtensions API, the same standard Chrome uses, but it cannot install packages from the Chrome Web Store as they are. Mozilla's porting guide says extensions written for Chrome will, in most cases, run in Firefox with a few changes. Those changes have to be made in the extension's code and submitted to Mozilla for signing, so a regular user cannot do them with a click.
That is why you will not find a working "Add to Firefox" button on Chrome Web Store pages. Chrome's store only offers its own browser, and Firefox only installs signed add-ons from Mozilla's catalogue or from the developer's own signed download.
For you as a user this means one rule: look for the Firefox edition of the extension, not for a way to convert the Chrome one. Extensions from the same developer usually behave the same way in both browsers, because they share most of their code.
How to get a Chrome extension's Firefox version
The fastest way is to search addons.mozilla.org for the extension's name and install the listing from the same developer. These steps work in Firefox on desktop.
- Note the exact name and developer of the Chrome extension you want.
- Open addons.mozilla.org in Firefox and search for that name.
- Open the listing whose developer matches the Chrome version, then click "Add to Firefox".
- Review the permission prompt and confirm only if the requested access makes sense for what the extension does.
- If AMO has no listing, check the developer's website or GitHub page for a Firefox download, and look for a similar extension in the best Firefox add-ons list.
Mozilla also highlights hand-reviewed "Recommended" extensions on the AMO home page, which is a safer starting point than unknown listings. Names alone can be copied, so always compare the developer and the number of users before you install.
If you are moving from Chrome, our list of the best Chrome extensions is a handy checklist: many of them have a Firefox twin.
What happened to Chrome Store Foxified?
Chrome Store Foxified was a Firefox add-on that converted Chrome Web Store extensions on the fly, and it no longer works on current Firefox. Its author said in September 2018 that he would stop working on it. The project's GitHub page now states that the extension is not working with the latest versions of Firefox.
When this article was first written in 2016, the add-on added an "Add to Firefox" button to Chrome Web Store pages. It downloaded the extension, converted it from the Chrome format (crx) to the Firefox format (xpi), edited the manifest.json file, and installed the result either as a temporary add-on or as a signed one through a Mozilla account.
The screenshots below show how that workflow looked at the time. They are kept for reference only, and you should not follow them on a current Firefox version.




How developers test a Chrome extension in Firefox
Developers can load an unpacked Chrome extension into Firefox as a temporary add-on to see whether it runs. This is a testing method, and the extension disappears when Firefox restarts.
- Type
about:debuggingin the Firefox address bar. - Select "This Firefox".
- Click "Load Temporary Add-on".
- Pick the extension's manifest.json file, or a packaged .zip.
Mozilla says the temporary add-on stays until you remove it or restart Firefox. To keep an extension permanently, it has to be packaged and submitted to AMO for signing, for example with Mozilla's web-ext tool. Mozilla also recommends running its validator on the manifest and checking the code against the list of Chrome incompatibilities.
Unofficial converters and "crx to xpi" websites cannot give you a signed, updatable add-on, and they ask you to trust code you did not get from the developer or Mozilla. Skip them.
Why some Chrome extensions do not work in Firefox
Some Chrome extensions fail in Firefox because they use Chrome-only APIs or manifest keys that Firefox does not implement. Mozilla documents the differences on MDN. The table lists the ones you are most likely to hear about.
| Area | Chrome | Firefox |
|---|---|---|
| Debugger and declarativeContent APIs | Available | Not implemented |
| Side panel | side_panel key and sidePanel API | sidebar_action key and sidebarAction API |
| Fixed extension ID | "key" property | browser_specific_settings.gecko.id |
| Background code (Manifest V3) | Service workers | Non-persistent background scripts (event pages) |
Firefox supports Manifest V3 since Firefox 109 and also continues to run Manifest V2 extensions, so developers can ship the same extension for both browsers with some manifest changes. Extensions that rely on the missing APIs, or on Chrome services such as Chrome sync, need a rewrite or have no Firefox equivalent.
If an extension you need is missing, ask the developer for a Firefox release. Many only need to be submitted to AMO.
FAQ
Does Firefox support Manifest V3 extensions?
Yes. Firefox made Manifest V3 generally available in version 109, and it keeps supporting Manifest V2 as well. Firefox uses event-driven background scripts instead of service workers.
Is it safe to install a converted Chrome extension from a third party?
Avoid it. Converted files are not signed by Mozilla and do not get automatic updates, and you have to trust whoever repacked the code. Install the developer's official Firefox listing instead.
Can the same extension work in both Chrome and Firefox?
Often yes. Developers can share most code between both browsers, and Mozilla says that Chrome extensions need only a few changes in most cases. Each browser still needs its own store listing.
Related: Best Firefox add-ons | Best Chrome extensions | How to restart Chrome without extensions
Chrome Store Foxified has been discontinued:
https://addons.mozilla.org/en-US/firefox/addon/chrome-store-foxified/
https://github.com/Noitidart/Chrome-Store-Foxified/issues/122
Now chrome store foxified is not working . It shows something else
Have installed Chrome Store Foxified as I use Lazarus Form Recovery and it has been disabled in the latest FF version. When I go to the extension in the Chrome webstore there is no “Add to Firefox” button. I have tried uninstalling and reinstalling Foxified a number of times but the problem persists.
There has been some changes apparently. I hope to fix them soon – https://github.com/Noitidart/Chrome-Store-Foxified/issues/60#issuecomment-299562743 – please excuse this.
Thanks for the courtesy of your swift response and I look forward to further developments.
I want to use Tunnello VPN. But it’s not currently able to access the Tunnello server. I can log in but cannot get it to change my IP address.
I Would Love The Alternate Option – Install FF Extensions In CHROME.
FEBE Would Be An Awesome Addition To CHROME.
Cheers.
I tried adding the beta version of Cybrhome and it WILL NOT let me sign for anything. I don’t know what the issue is. I don’t care for the Alpha version which Firefox already has. There HAS to be a way around it without adding it temporarily. I was super existed about Firefox 48 because I thought I could use this extension but so far no dice. :(
Came to comment on that god-Fugly theme. Whoever uses this ‘theme’ has sh*t taste.
>Sadly, it probably won’t survive the demise of XUL. Mozilla deserves to fade into oblivion if they treat their users this way.
Lel, thank God, so we won’t see any more abominations of themes. Eye-cancer to the fullest.
Dear Martin,
Thank you very much for writing this article on Chrome Store Foxified.
One of the main features of the addon, is that you do not need to be logged in with a Google account to download addons from their store. Unfortunately, to sign the addon, you do have to have an account at addons.mozilla.org
I am currently working on version 2.0 which supports Android. The WebExtension API team added support for Android, and Foxified in its current format will not work there.
Version 2 also has better error messages. The signing process does not sign all addons, it has issues. In version 2 I try to make things more clear.
Version 2 also has a more interactive GUI. I found that many users did not know about the “options” of foxified, so I am bringing all the buttons into the forefront.
And of course some bug fixes. Version 2 does not have the elegant notification bar seen in v1.x – as that is a desktop only feature. In a future 2.x version I’ll bring it back. But the Firefox for Android support was my priority in v2.0
Really appreciate this article!
Side note:
Please check out this other addon I recently made.
I worked on a multi monitor screenshot addon that is pretty unique, when compared to all the other firefox screenshot addons out there. It is cross platform, and similar to Lightshot. No middelman servers in my addon though. For instance, when you upload to imgur, it uploads to imgur and returns to you the imgur link. Not a link routing through a 3rd party server like nimbus.com or prntscr.com.
It is called NativeShot – https://addons.mozilla.org/en-US/firefox/addon/nativeshot/ – a cool feature is a global hotkey option (enabled by default) that replaces the system “Print Screen” button with NativeShot’s feature, works even when Firefox is not focused.
Thanks!
I thought AH was dead.
I really have the feeling that that is the wrong person which you had in mind :D
I don’t know what you mean. I was thinking Alfred Hitchcock.
Someone once claimed that Firefox was not a Chrome wannabe.
OK, Martin indeed wrote the article “No, Firefox won’t become a Chrome clone”. However, he is clearly critical towards Mozilla. In my opinion his writings are fairly balanced in content. This is what I appreciate about him.
The true Mozilla apologist and Mozilla Representative, the one who will dismiss every criticism towards Mozilla as trolling, and the defender of even the most stupid decisions Mozilla has ever made, sits elsewhere. I won’t mention his name since he will come at me and complain about my “false judgement” and “lies” I spread about him. He is the owner of a fairly influential Firefox blog in the German-speaking area. It is anyone’s guess whom I mean.
Finest cuisine :)
I’ve always appreciated so-called “strong characters” but at the same time their excessive enthusiasm when not passion may lead them to martial, essentially subjective judgements about other opinions than theirs and, far more irritating, judgements about their very detractors. It’s not that they are bad, it’s only that they conceive pluralism as incompatible with the universal one and only truth which they happen to know. A fundamentally idealistic approach, almost a religious one if it weren’t that in their scenario god happens to be themselves, which is problematic for us all, poor ignoramus and sinners alike :)
Sure, the ability to install Chrome extensions in Firefox is pretty cool. However, it will probably never become fully operational, seeing that Firefox lacks the Blink rendering engine. Furthermore I don’t understand why Mozilla cannot keep the XUL-based extensions. Firefox 48 will obviously feature both methods.
XUL is on its way out. The Firefox of the future will only feature a WebExtensions Add-On system. This essentially removes the need to use Firefox. Why should I use a then inferior browser if I could use Chrome just as well? This is why I have to disagree with the following quote from the article:
“This could give Firefox a major edge over Mozilla considering that Chrome users cannot install legacy Firefox add-ons at all as they are not based on WebExtensions.”
It will only provide a temporary edge to Mozilla for obvious reasons. XUL will be deprecated in the very near future. In my opinion the Mozilla management is therefore just incompetent. They honestly think they could sway over users with maximum compatibility to Chrome. Again: Why shouldn’t I just use Chrome then? It makes no sense. By killing off XUL they will disappoint even the last power user still faithful to them. This is the hardcore fanbase, the ones who recommend Firefox to the DAUs. Mozilla, I wish you good fortune in the browser wars to come…
I switched to Pale Moon when it first came out. One of my PCs is an old P4 running XP.
I have been quite happy with the Atom build. It’s fast and it still runs all my addons.
I can’t see the Pale Moon team getting into this Chrome wannabe mentality.
Once the Mozillians upset the die hard user community Firefox will be on its way out.
I agree 500% with you all the line, myself I’M migrating slowly to Vivaldi who care for Power USers and I will certainly brings many casual users (Customers) with me on the run if I’m satisfied, Since last year I begun to suggest Chrome for my casual users/customers, before it was Firefox.
I wonder how will Mozilla convince their users in two or three years to stay with their browser and not switch to Chrome…
I agree, particularly with the proprietary API that Chrome addons Devs will take advantage.
No point for a casual users to stay with Firefox over Chrome and lot of power users/Dev like me are switching over Chromium forks like Vivaldi who target especially Power Users that were abandoned by Mozarella.
“I wonder how will Mozilla convince their users in two or three years to stay with their browser and not switch to *Vivaldi* ”
FTFY :) I think Mozilla’s power users will be moving to Vivaldi. it’s just a matter of time for me.
There are already so many Mozilla extensions and this ganging up with Google is not my cup of tea when I dislike the company and avoid it as much as I can, anyway far more than it avoids me. Anyway, for those who are happy about this perspective, that of erasing borders between two companies that everything differentiates, have fun.
@ Tom Hawack
Is Google investing in Mozilla to broaden its user data acquisition base ?
I think we need to be told :)
@gh,
The Google cookie is related to Firefox’s built-in Safebrowsing feature, but disabling Safebrowsing once the cookie is installed doesn’t seem to allow removing that cookie from Firefox itself.
Best way to proceed if you decide to NOT use safebrowsing :
1- Disable all Safebrowsing occurences in Firefox’s about:config (this can be added to your user.js file) :
// disable safebrowsing
user_pref(“browser.safebrowsing.enabled”, false);
user_pref(“browser.safebrowsing.malware.enabled”, false);
user_pref(“browser.safebrowsing.appRepURL”, “”);
user_pref(“browser.safebrowsing.downloads.enabled”, false);
user_pref(“browser.safebrowsing.downloads.remote.enabled”, false);
user_pref(“browser.safebrowsing.gethashURL”, “”);
user_pref(“browser.safebrowsing.malware.reportURL”, “”);
user_pref(“browser.safebrowsing.provider.google.appRepURL”, “”);
user_pref(“browser.safebrowsing.provider.google.gethashURL”, “”);
user_pref(“browser.safebrowsing.provider.google.reportURL”, “”);
user_pref(“browser.safebrowsing.provider.google.updateURL”, “”);
user_pref(“browser.safebrowsing.provider.mozilla.gethashURL”, “”);
user_pref(“browser.safebrowsing.provider.mozilla.updateURL”, “”);
user_pref(“browser.safebrowsing.reportErrorURL”, “”);
user_pref(“browser.safebrowsing.reportGenericURL”, “”);
user_pref(“browser.safebrowsing.reportMalwareErrorURL”, “”);
user_pref(“browser.safebrowsing.reportMalwareURL”, “”);
user_pref(“browser.safebrowsing.reportPhishMistakeURL”, “”);
user_pref(“browser.safebrowsing.reportPhishURL”, “”);
user_pref(“browser.safebrowsing.reportURL”, “”);
user_pref(“browser.safebrowsing.updateURL”, “”);
2- Restart Firefox;
3- Exit Firefox;
4- Delete the cookies.sqlite file in your Firefox profile ; THIS WILL DELETE ALL YOUR COOKIES, Google’s included
5- Restart Firefox
Of course every visit of a Google site will recreate a cookie but this time Firefox’s cookie manager will be able to delete new Google cookie. You can also use the excellent Firefox add-on called ‘Self-Destructing Cookies’
Never experienced this persistent Google cookie myself, perhaps because Safebrowsing is disabled here and that all cookies had been deleted after that.
@gh: Of course I can verify my claims. :-)
To be exact, it is the so-called PREF cookie. It is connected to a Google domain (google.com) and contains a unique ID number. The PREF cookie is known to be used by the NSA and GCHQ in order to spy on people. Moreover it will appear after every single Firefox restart, which means that it will be recreated even if it was deleted previously.
The good news is: If you know how, you may be able to disable it. For more information check out these links on the topic (from which I got my information):
http://stackoverflow.com/questions/6301114/how-pref-cookie-google-com-appears-in-firefox
https://bugzilla.mozilla.org/show_bug.cgi?id=368255
“Firefox contains a non-deletable Google Super Cookie. Even when you deactivate cookies entirely it is still there.”
Would you please elaborate — asking because I’ve not witnessed this.
When is this supercookie created?
How did you discover it?
Where should I look to find evidence of its existence?
@Gary D
Mozilla’s 5-year contract with Google ended a couple of years ago. They’re partnered with Yahoo! now.
@Gary D and Tom Hawack: Firefox contains a non-deletable Google Super Cookie. Even when you deactivate cookies entirely it is still there. I don’t think this needs further explanation. Everyone who believes that Firefox is more private than Chrome is naive.
Gary D, I have no idea of a hidden plan, I’m not into the plot hysteria so with you I’d care to be told, if applicable.
Rather I have the feeling we’re just in a life scheme where the strongest smiles to the weakest, waiting for the profits of sympathy which take a little longer than those obtained by struggle but which last much longer. To resume, diplomacy is sometimes a gentleman’s agreement to beat the opponent in a civilized way. And we all know that strength and virtue are not corollary :)
but what is this? Opera browser? gosh… maybe in the next 2 years mozilla is announcing that there is no point on having an add ons page when you have chrome’s one and they will shut down firefox extensions page… because, seriously, this idea for me just seems stupid…
firefox has already great extensions and basically almost all the extensions that are actually useful already have been ported… ofc, this makes the life easier for extension devs, but seriously, having to go into chrome’s add on page with a browser that has nothing to do with chrome and download the extensions? just seems odd to me…
That addons tab looks so wrong..
It’s the alternative Add-Ons manager which you can select using “Classic Theme Restorer”.
@ns: True that. Sadly, it probably won’t survive the demise of XUL. Mozilla deserves to fade into oblivion if they treat their users this way.
Thank god for CTR!
@Peter
“That addons tab looks so wrong…”
Instead of making a bald statement like this, please explain WHY it looks so wrong so that we lesser, unobservant, mortals can learn something.
That’s the whole point of forums: education,enlightenment, understanding.
What a good news this is ! Thank you for the info, Martin.
WebExtensions are great. Chrome extensions like moarTLS Analyzer (source code) will be able to run easily in Firefox without the need to rewrite code.